Skip to content

XtensaAsmPrinter: add a missing case for MBB (LLVM-456) #114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: xtensa_release_19.1.2
Choose a base branch
from

Conversation

yamt
Copy link

@yamt yamt commented Jul 4, 2025

fixes an assertion failure:

Assertion failed: (ACPV->isExtSymbol() && "unrecognized constant pool value"), function emitMachineConstantPoolValue, file XtensaAsmPrinter.cpp, line 110.

observed with wamr-compiler.

@github-actions github-actions bot changed the title XtensaAsmPrinter: add a missing case for MBB XtensaAsmPrinter: add a missing case for MBB (LLVM-456) Jul 4, 2025
fixes an assertion failure:
```
Assertion failed: (ACPV->isExtSymbol() && "unrecognized constant pool value"), function emitMachineConstantPoolValue, file XtensaAsmPrinter.cpp, line 110.
```
observed with wamr-compiler.
@yamt yamt force-pushed the asm-printer-mbb branch from b474986 to 7ae6c31 Compare July 22, 2025 08:31
@espressif-bot espressif-bot added Status: In Progress work is in progress and removed Status: Opened labels Aug 7, 2025
@espressif-bot espressif-bot added Status: Done Issue is done internally Resolution: NA and removed Status: In Progress work is in progress labels Aug 12, 2025
@andreisfr
Copy link
Collaborator

@yamt. thank you very for investigation of the problem. This problem will be fixed in next release soon.

@yamt
Copy link
Author

yamt commented Aug 13, 2025

@yamt. thank you very for investigation of the problem. This problem will be fixed in next release soon.

thank you for taking a look at this.
do you mean the next release which will be based on llvm-20? (just asking)

@gerekon
Copy link
Collaborator

gerekon commented Aug 13, 2025

@yamt. thank you very for investigation of the problem. This problem will be fixed in next release soon.

thank you for taking a look at this. do you mean the next release which will be based on llvm-20? (just asking)

Yes. It will be based on LLVM 20.1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: NA Status: Done Issue is done internally
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants